…h > 1 carry value

though this should never happen in practice since we only call loop range(3) times,
so +0, +1, and +2. Even a 4-channel light could only carry once, so
really this should only matter in the 5+ channel case (or perhaps if you
can start with an offset of +3, which really should be a carry+1 with 0 offset

for readability. The config params are generally pulled out inside the initialize
in these, rather than from the self config reference within the function -- this
is intentional to try and keep config reading inside initialize itself

…rought execution order for readability

to better orient the seams with the data structures and relevancy

…rmware support

…r ER command support

.44 provided the ER command, but .48 provides 128 as the light-limit-per-header
and has extended support for RGB-RGBW mixed chains

required an ER: message processor in order to not block past getting the ER:P response

…de lights

…tion

under the hood the light breakouts are considered "local breakouts", so the
dev will define light overrides there, not inside the "breakouts" config

added a new config option, which is 1-based (since LED numbers in FAST are 1 based)
and support in ER command when setting mixed mode